Configuring the electronic signature data

The data that is included in an electronic signature is entirely up to you. The data should be stored in the built-in Meridian Enterprise property AMDocumentPropertySet._ESIGNATURES. The value of this property is shown when users click the Electronic signatures link on the Document page in PowerUser and the value is used to render signature pages for renditions created by BlueCielo Publisher. You can combine and format the data from document properties, user input, and any other data available to VBScript.

To configure the electronic signature data:

1. In Meridian Enterprise Configurator, in the VBScript editor, add code to the event handler that corresponds to the beginning of the workflow for which you enabled electronic signatures as described in Configuring electronic signatures for document type workflow and Configuring electronic signatures for workflow definitions.

   • For document type workflow transitions: DocWorkflowEvent_AfterChangeWFState
   • For workflow definition transitions: ProjectWorkflowEvent_AfterExecuteTransition

   Your code should test for the correct starting transition name and it should empty the property of any electronic signatures that were made for the prior revision of the document similar to the following example fragment.

Document.Property("AMDocumentPropertySet._ESIGNATURES")=vbNullString

2. Add code to the same event handler but for the end workflow transition. Your code should test for the correct end transition name and concatenate the new electronic signature data to any prior electronic signatures that may have been made within the same workflow. Your code should look similar to the following example fragment. This example stores the user's name, the current date, and the reason that the user entered when they signed the document.

Document.Property("AMDocumentPropertySet._ESIGNATURES")= _
Document.Property("AMDocumentPropertySet._ESIGNATURES") & _
"Electronically signed by: " & User.FullName & _
" on: " & Today & _
" reason: " & Batch.Argument("ESigReason") & vbCrLf

Note    This example uses a batch argument to retrieve the reason for the electronic signature. The argument could have been set by a wizard page or other scripting. Other methods can also be used. For more information about using batch arguments, see the BlueCielo Meridian Enterprise VBScript API Reference.